<?xml version="1.0" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="..\..\XSLTemplates\ErrorsStyleSheet.xsl"?>
<Error>
<ErrorNumber>2060</ErrorNumber>
<ErrorFamily>Non-Volatile Storage</ErrorFamily>
<ErrorMessage>
NVS: checksum error in DAOM profile block
</ErrorMessage>
<AppliesTo>
<UnnumberedList>
<ListItem><Text>Green</Text></ListItem>
</UnnumberedList>
</AppliesTo>
<ServiceInformation>
<DescriptionText><text>
The DAOM profile saved on the MPE is un-initialized or corrupted.  A "daom cal" command must be
performed before stroke calibration or edge searching.
</text></DescriptionText>
<DescriptionText><text>
Since all subsystems are normally initialized when a recorder is integrated, this error should not occur
during normal operation, except possibly during firmware upgrades.
</text></DescriptionText>
<DescriptionText><text>
The firmware determines whether the DAOM profile is valid or corrupt with a checksum "hidden" at the
end of the profile. A corrupt checksum is corrected when a profile is saved using "nvs save daom".
</text></DescriptionText>
<DescriptionText><text>
If firmware has been downloaded recently, this error could be due to an incomplete upgrade (or
downgrade) procedure and can be safely ignored until the upgrade is complete.  Note that the "nvs
upgrade" command should not be used more than once per upgrade.  Therefore, if you are uncertain
whether or not the upgrade command has been issued since the download, it is safer not to use it.
</text></DescriptionText>
<DescriptionText><text>
If the DAOM profile has been saved in the past, and if a firmware download has not been performed since
the last time the DAOM profile was used (i.e. stroke calibration, edge search), a more serious cause is
possible and the error message should be reported to the responsible firmware programmer.  The NVS part
on the MPE could be failing, or a firmware bug could be responsible (version 1.57 had such a bug).  The
calibration can be re-saved, but corruption may re-occur.
</text></DescriptionText>
<DescriptionText><text>
No matter what the cause of this error, and unless the "nvs upgrade" command can be used safely, the
DAOM should be re-calibrated ("daom cal") and then saved ("nvs save daom").
</text></DescriptionText>
</ServiceInformation>
<OperatorAction>
<DescriptionText><text>
Record error message and contact Creo Service
</text></DescriptionText>
</OperatorAction>
<Cause>
Firmware upgrade (or downgrade) in progress - should be fixed by "nvs upgrade" command
</Cause>
<Cause>
NVS never properly initialized
</Cause>
<Cause>
Version mismatch between current firmware and firmware that created "fload memory" file
</Cause>
<Cause>
NVS corrupted by firmware bug
</Cause>
<Cause>
Faulty NVS part on MPE
</Cause>
<SeeAlso>
<UnnumberedList>
<Link><LinkAddress>../commands/daom.xml</LinkAddress><LinkTitle>Command: daom</LinkTitle></Link>
</UnnumberedList>
</SeeAlso>
<OtherLinks>
<Link><LinkAddress>..\..\ShowAllErrors.htm</LinkAddress><LinkTitle>Firmware 0 Error Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllCommands.htm</LinkAddress><LinkTitle>Firmware 0 Command Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllNVS.htm</LinkAddress><LinkTitle>Firmware 0 NVS Index</LinkTitle></Link>
</OtherLinks>
<Updated>
Updated: Wed Jul 16 19:32:17 2008 PST
</Updated>
<Links>
</Links>
</Error>
